Oracle Retail Order Broker/Oracle Retail Order Management System Configuration (Order Broker)

Purpose: This topic describes the required setup to integrate Oracle Retail Order Management System with Oracle Retail Order Broker, and how to load item and inventory information from Oracle Retail Order Management System into the Oracle Retail Order Broker database.

Default system? When you begin setting up data in Oracle Retail Order Broker, you build a location group of integrated systems, such as your Oracle Retail Order Management System company and your POS system. If your Oracle Retail Order Management System company is the default system, or system of record, in Oracle Retail Order Broker, then when you import your Oracle Retail Order Management System item and SKU records into Oracle Retail Order Broker, they serve as the master products, and the product records imported from other systems reference the Oracle Retail Order Management System items and SKUs. The Oracle Retail Order Management System item and SKU code is the product code in Oracle Retail Order Broker, and the product codes from other integrated systems are system products that reference the product code from the default system.

If Oracle Retail Order Management System is not the default system in Oracle Retail Order Broker, then each item and SKU sent to Oracle Retail Order Broker needs to reference the product code from the default system. If the systems use different product codes, you can use a secondary field in Oracle Retail Order Management System, such as the Reference number or a UPC code, to store the Oracle Retail Order Broker product code, so that the Oracle Retail Order Management System system product is correctly linked to the default system’s product code during the import process. The OROB Product Code ID (K66) system control value indicates whether the Oracle Retail Order Management System item and SKU, or some other field, contains the default system’s product code.

For more information: See:

• background on integration between Oracle Retail Order Broker and Oracle Retail Order Management System: the Oracle Retail Order Broker Integration Overview

• details on the order types, processing, and messages: Order Broker Integration

• instructions on setting up data in Oracle Retail Order Broker: the Setting Up Data for the Order Broker Module topic in the Oracle Retail Order Broker online help

• instructions on setup required for integration with Oracle Retail Order Broker’s Supplier Direct Fulfillment module: Interface with Oracle Retail Order Broker’s Supplier Direct Fulfillment Module: Overview and Setup

Version compatibility: Release 5.0 or higher of Oracle Retail Order Management System is compatible with release 5.0 or higher of Oracle Retail Order Broker. Integration with release 3.0 or 3.1 of Oracle Retail Order Broker is also supported, although features added since that release, such as the ability to send held orders to Oracle Retail Order Broker, are not available.

In this chapter:

• Order Broker-Related System Control Values

• Oracle Retail Order Broker Properties

- WSDL Location (version 5.0 or higher)

- Endpoint URL’s (version 3.0 or 3.1)

- Setting the Daily Status Inquiry Time Window (all versions)

- Message Version Number

• Additional Oracle Retail Order Broker Setup in Oracle Retail Order Management System

• Notes on Configuration in Oracle Retail Order Broker

Order Broker-Related System Control Values

Most of the system control values related to integration with Oracle Retail Order Broker’s Order Broker are available through the Order Broker Values (K15) umbrella screen. See that screen for more information.

Special orders system control values: The following system control values are required to process special ship-to-store orders:

• Order Type for Special Orders (L15): Identifies the order type code that indicates to send the e-commerce order number, rather than the Oracle Retail Order Management System order number, as the order ID when submitting the ship-to-store order to the Order Broker. Since special ship-to-store orders originate in the retail location, they are identified primarily by the store system’s original order number.

• Pay Type for Special Orders (L16): Identifies the pay type that indicates that the customer needs to pay for a ship-to-store order when picking it up at the retail location. When a ship-to-store order uses this pay type, the Submit Order message indicates a balance_due that is the same as the order total.

• Store Pickup Confirmation Email Program (L48): Use this system control value to specify the program that generates a notification to the customer when a store pickup order is ready for pickup.

Additional system control values:

• To avoid an error in order entry, do not set the Default Previous Pay Type in Order Entry (D64) system control value to ALL; otherwise, the Order Broker Payment Type (K98) might default in order entry, although this pay type is reserved for delivery or retail pickup orders created through integration with the Order Broker.

• Use OROB Status Inquiry List Web Service (M05): Select this system control value to have pick slip generation use the status list request message rather than individual status inquiry request messages to check on whether retail pickup or delivery orders have been canceled by the originating system.

Oracle Retail Order Broker Properties

Overview: Use Working with Customer Properties (PROP) to define property settings for:

• WSDL Location (version 5.0 or higher)

• Endpoint URL’s (version 3.0 or 3.1)

• Setting the Daily Status Inquiry Time Window (all versions)

• Message Version Number

• Endpoint for Location Discovery Web Service

Purchasing services properties: See Interface with Oracle Retail Order Broker’s Supplier Direct Fulfillment Module: Overview and Setup for information on the additional properties related to integration with Oracle Retail Order Broker’s Supplier Direct Fulfillment module.

WSDL Location (version 5.0 or higher)

If you integrate with Oracle Retail Order Broker version 5.0 or higher: Use the OROB_SERVICES_WSDL_LOCATION property in Working with Customer Properties (PROP) to specify the location of the WSDL (web service definition language) for the locate services web service. For example: OROB_SERVICES_WSDL_LOCATION=file:///usr/local/tomcat01/conf/cwdirectcpproperties/LocateServices.wsdl.

Open the WSDL file and change the address location to the endpoint for the Locate web service. This entry should be set to https://SERVER:8443/Locate/LocateServices, where SERVER is the name of your Oracle Retail Order Broker server.

Also required for Supplier Direct Fulfillment integration: You need to set this property as described above even if you integrate with Oracle Retail Order Broker’s Supplier Direct Fulfillment module but not with Oracle Retail Order Broker’s Order Broker module, or if you integrate with an earlier version of Oracle Retail Order Broker for the Order Broker than you use for the Supplier Direct Fulfillment module.

Web service authentication: If the web service requires basic web service authentication, you must define a valid web service authentication user and password in Working with Web Service Authentication (WWSA).

Note: You must stop and restart Oracle Retail Order Management System before your change takes effect.

Endpoint URL’s (version 3.0 or 3.1)

If you integrate with Oracle Retail Order Broker version 3.0 or 3.1: Specify the endpoint URL’s for the web service that manages communication between the two systems. URL-related entries are:

CW_GET_STATUS_SERVICE_ENDPOINT_URL=http://SERVER/LOCATE/service/locate.asmx

CW_GET_LOCATION_SERVICE_ENDPOINT_URL=http://SERVER/LOCATE/service/locate.asmx

CW_SEND_STATUS_SERVICE_ENDPOINT_URL=http:/SERVER/LOCATE/service/locate.asmx

CW_SEND_ORDER_SERVICE_ENDPOINT_URL=http://SERVER/LOCATE/service/locate.asmx

CW_FULFILLMENT_SERVICE_ENDPOINT_URL=http://SERVER/LOCATE/service/locate.asmx

where SERVER is the name of the server where Oracle Retail Order Broker is running and LOCATE is the name of the Oracle Retail Order Broker database and the account specified in the OROB Account (K49) system control value.

Setting the Daily Status Inquiry Time Window (all versions)

Applies to retail pickup and ship-to-store orders: For certain Order Broker statuses, it is not necessary to send a status inquiry as frequently as the Order Broker Status Update Interval (K10), because no immediate action is required in Oracle Retail Order Management System. These statuses apply to retail pickup or ship-to store orders:

• In transit: the order has been shipped to the store location

• received: the order has been received at the store location, but the customer has not yet picked it up

• partially fulfilled: the customer has picked up some of the items, or quantity of items on the order, but has not yet received the entire order

In order to avoid sending unnecessary status inquiry messages for orders in these statuses, the BROKER process checks their status once daily during a specified time window. It uses the following two additional properties in Working with Customer Properties (PROP) to determine the start and end of the window:

• OROB_LIMITED_STATUS_BEG_TIME=123456

• OROB_LIMITED_STATUS_END_TIME=123456

Each time is indicated in HHMMSS format, military time. For example, if you set these properties to:

OROB_LIMITED_STATUS_BEG_TIME=180000

OROB_LIMITED_STATUS_END_TIME=210000

Then the BROKER process can send status inquiry requests for these orders between 6:00 p.m. and 9:00 p.m. daily. Orders are eligible for status inquiry if one has not taken place in the previous 12 hours.

You should set the time window long enough to process status inquiries for all orders in the related statuses; also, the time window should not cross midnight.

Message Version Number

Use the following entry to specify the message version to include in Order Broker and merchandise locator request messages that Oracle Retail Order Management System sends to Oracle Retail Order Broker:

OROB_MESSAGE_VERSION=5.0

Set this property to 3.0 or 3.1 if you integrate with Oracle Retail Order Broker version 3.0 or 3.1; otherwise, set this property to 5.0 or higher, based on the corresponding Oracle Retail Order Broker version.

Required for status list request and streamlined allocation: A message version of 5.0 or higher is required to use the status list request message and streamlined allocation at pick slip generation. See Use OROB Status Inquiry List Web Service (M05) and Use Streamlined Allocation (L63) for background.

Important: To avoid unpredictable results, do not leave the OROB_MESSAGE_VERSION blank.

Endpoint for Location Discovery Web Service

Use the OROB_DISCOVERY_SERVICES_WSDL_LOCATION entry in Working with Customer Properties (PROP) to specify the location of the WSDL (web service definition language) for the location discovery web service, used to create new Store Cross Reference records in Oracle Retail Order Management System based on existing location records in Oracle Retail Order Broker. This entry should be set to file:///usr/local/tomcat01/conf/cwdirectcpproperties/DiscoveryServices.wsdl.

Open the WSDL file and change the address location to the endpoint for the location discovery web service. This entry should be set to https://SERVER:8443/Locate/DiscoveryServices, where SERVER is the name of your Oracle Retail Order Broker server.

Note: You must stop and restart Oracle Retail Order Management System before your change takes effect.

For more information: See Importing Store Cross Reference Locations through Oracle Retail Order Broker’s Discovery Web Service.

For more information:

Additional Oracle Retail Order Broker Setup in Oracle Retail Order Management System

Purpose: Additional setup for integration with Oracle Retail Order Broker is described below:

General Oracle Retail Order Broker setup:

• Unselect the OROB eligible flag for any items that should not be included in the Oracle Retail Order Broker integration. This flag is selected by default.

• Complete the Locate location for each warehouse that maps to a location in Oracle Retail Order Broker. If the Send Inventory by Warehouse to OROB (L06) system control value is selected:

- the product import process sends inventory information separately for each warehouse that has a Locate location specified.

- the BROKER process sends a separate fulfillment request message for each warehouse that has a Locate location specified.

Order Broker setup:

• BROKER process in Working with Integration Layer Processes (IJCT):

- Set up any trigger rules for brokered backorders. The fields in the Item (INITEM) and SKU (INSKU) tables are available for trigger rule setup.

- Optionally, set the Outbound delay time. The Outbound delay time controls how often to send fulfillment request messages.

• Secured features:

- Use the Cancel Order Broker Lines (B19) secured feature to restrict access to Order Broker cancellations as needed.

- Use the Maintain Brokered Fulfillment Orders (B20) secured feature to restrict access to order maintenance for retail pickup or delivery orders.

• Store cross references: Create store location cross references for each potential fulfilling location through Work with Store Cross Reference (WSCR), including:

- optionally, specify a source code for any store location to send retail pickup or delivery orders to Oracle Retail Order Management System as an override to the Order Broker Source Code (K93). If the fulfillment response message specifies a source code, it overrides any source code specified in the system control value or the store cross reference.

- for ship-to-store orders, select the Ship to store flag; also, complete the description and address fields, as this information is used as the ship-to name and address for ship-to-store orders.

- optionally, specify a System Code to override the Name in OROB for Point of Sale (L09) used to identify the fulfilling location for ship-to-store and store pickup orders

Note: You can use the Importing Store Cross Reference Locations through Oracle Retail Order Broker’s Discovery Web Service option to create store cross reference records.

• BROKER periodic function: Set up and schedule the BROKER periodic function (program PFR0083) to generate requests for existing backordered lines.

Note: Since the BROKER periodic function should not run at the same time as pick slip generation, the periodic function runs in the PICKGEN queue regardless of your selection for the periodic process.

• Schedule BROKER process: Optionally, set up periodic functions to schedule the BROKER process in Working with Integration Layer Processes (IJCT):

- ENDBROK (program=ILENDBROKR) to stop the BROKER process

- STRBROK (program=ILSTRBROKR) to start the BROKER process

• CWPickOut: If you use the CWPickOut message to send pick slip information from Oracle Retail Order Management System to an external system, set the Outbound XML version of the PICK_OUT process in Working with Integration Layer Processes (IJCT) to 3.0 or higher to include:

- broker_delivery_type of R (retail pickup), D (delivery), or S (ship-to-store)

Note: This field is not used for brokered backorders.

- destination_store: the store cross-reference code (WSCR) for a ship-to-store order

- originating_store: the store cross-reference code (WSCR) for a retail pickup or delivery order

• CWInvoiceOut: If you use the CWInvoiceOut message to send invoice information to an external system, set the Outbound XML version of the INVOIC_OUT process in Working with Integration Layer Processes (IJCT) to 2.0 or higher to include:

- ost_broker_delivery_type of R (retail pickup), D (delivery), or S (ship-to-store)

Note: This field is not used for brokered backorders.

- ost_destination_store: the store cross-reference code (WSCR) for a ship-to-store order

- ost_originating_store: the store cross-reference code (WSCR) for a retail pickup or delivery order

• Email setup: Use the Email notification flag to control email generation for the retail pickup, delivery, or store pickup order types. Also, set up the store pickup notification template. See Email Generation Setup for more information.

Merchandise locator setup: For merchandise locator searching: Make sure the MERCH_LOC process in Working with Integration Layer Processes (IJCT) has its Communication type field set to Web Service.

Notes on Configuration in Oracle Retail Order Broker

Follow the steps described under Setting Up Data in Oracle Retail Order Broker in the Oracle Retail Order Broker online help or operations guide, using the following notes to configure the integration between Oracle Retail Order Broker and Oracle Retail Order Management System:

System setup:

• Default system? If Oracle Retail Order Management System is the default system for your organization, set the OROB Product Code ID (K66) system control value in Oracle Retail Order Management System to Item/SKU or blank. Otherwise, if Oracle Retail Order Management System is not your default system, use the OROB Product Code (K66) system control value to indicate the field you use to store each item’s product code from the default system.

• Setting up the Oracle Retail Order Management System system: Also, when creating the Oracle Retail Order Management System system in Oracle Retail Order Broker:

- Set the System code in Oracle Retail Order Broker to match the Company number in Oracle Retail Order Management System and the OROB System (K50) system control value. The code should not be zero-padded (that is, create a system of 2 rather than 002).

- Select the Online flag.

- Set the Connection type to Direct DB.

- In the Connection string field, enter Server=SERVERNAME;Initial Catalog=OMS_db;Uid=user;Pwd=password; where SERVERNAME is the name of your database server, OMS_db is the name of your Oracle Retail Order Management System database, and user and password are a valid user ID and password for the database server.

Warehouse (location) setup:

• Create a location in Oracle Retail Order Broker to represent your default warehouse in Oracle Retail Order Management System. The location code in Oracle Retail Order Broker should match the warehouse number in Oracle Retail Order Management System, and should not be zero-padded (that is, create a warehouse of 1 rather than 0001).

• At the Preferences screen in Oracle Retail Order Broker, flag the default Oracle Retail Order Management System location, and any additional locations representing Oracle Retail Order Management System warehouses, as Pickup available = No. (NOTE: You can set this flag at the location type level if you have set up a location type to represent your Oracle Retail Order Management System warehouses; in this case, you do not need to set the flag for each individual location.)

Note: See the Oracle Retail Order Broker online help for additional steps to setting up data in Oracle Retail Order Broker.

Product and inventory import setup: Use the System Import Schedule screen to set up a schedule for importing items and inventory information from Oracle Retail Order Management System into Oracle Retail Order Broker. When setting up the schedule:

• Select the Enabled flag.

• Set the Import Process Type to Extract and Import.

• If Oracle Retail Order Management System is your default system, make sure to schedule its import process about 30 minutes earlier than any other systems to prevent product import errors. The product import will fail if you attempt to create a system product record before the product record for the default system exists.

Note: Schedule the product and inventory import so that it occurs after the purchase order layering process completes. See Purchase Order Layering for more information.